docs/development/Hardware Debugging in Eclipse.md

   1 # Hardware Debugging In Eclipse
   2
   3 Build a binary with debugging information using command line or via Eclipse make target.
   4
   5 Example Eclipse make target
   6
   7 ![](https://raw.github.com/wiki/hydra/cleanflight/images/eclipse-gdb-debugging/make 1 - OLIMEXINO GDB.PNG)
   8
   9 # GDB and OpenOCD
  10
  11 start openocd
  12
  13 Create a new debug configuration in eclipse :
  14 ![connect to openocd](http://i.imgur.com/somJLnq.png)
  15 ![use workspace default](http://i.imgur.com/LTtioaF.png)
  16
  17 you can control openocd with a telnet connection:
  18
  19      telnet localhost 4444
  20
  21 stop the board, flash the firmware, restart:
  22
  23      reset halt
  24      wait_halt
  25      sleep 100
  26      poll
  27      flash probe 0
  28      flash write_image erase /home/user/git/cleanflight/obj/cleanflight_NAZE.hex 0x08000000
  29      sleep 200
  30      soft_reset_halt
  31      wait_halt
  32      poll
  33      reset halt
  34
  35 A this point you can launch the debug in Eclispe.
  36 ![](http://i.imgur.com/u7wDgxv.png)
  37
  38 # GDB and J Link
  39
  40 Here are some screenshots showing Hydra's configuration of Eclipse (Kepler)
  41
  42 If you use cygwin to build the binaries then be sure to have configured your common `Source Lookup Path`, `Path Mappings` first, like this:
  43
  44 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 7.PNG)
  45
  46
  47 Create a new `GDB Hardware Debugging` launch configuration from the `Run` menu
  48
  49 It's important to have build the executable compiled with GDB debugging information first.
  50 Select the appropriate .elf file (not hex file) - In these examples the target platform is an OLIMEXINO, not a naze32.
  51
  52 DISABLE auto-build
  53
  54 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 1.PNG)
  55
  56 Choose the appropriate gdb executable - ideally from the same toolchain that you use to build the executable.
  57
  58 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 2.PNG)
  59
  60 Configure Startup as follows
  61
  62 Initialization commands
  63
  64 ```
  65 target remote localhost:2331
  66 monitor interface SWD
  67 monitor speed 2000
  68 monitor flash device = STM32F103RB
  69 monitor flash download = 1
  70 monitor flash breakpoints = 1
  71 monitor endian little
  72 monitor reset
  73 ```
  74
  75
  76 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 3.PNG)
  77
  78 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 4.PNG)
  79
  80 It may be useful to specify run commands too:
  81
  82 ```
  83 monitor reg r13 = (0x00000000)
  84 monitor reg pc = (0x00000004)
  85 continue
  86 ```
  87
  88 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 13.PNG)
  89
  90 If you use cygwin an additional entry should be shown on the Source tab (not present in this screenshot)
  91
  92 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 5.PNG)
  93
  94 Nothing to change from the defaults on the Common tab
  95
  96 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 6.PNG)
  97
  98 Start up the J-Link server in USB mode
  99
 100 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 9.PNG)
 101
 102 If it connects to your target device it should look like this
 103
 104 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 10.PNG)
 105
 106 From Eclipse launch the application using the Run/Debug Configurations..., Eclipse should upload the compiled file to the target device which looks like this
 107
 108 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 11.PNG)
 109
 110 When it's running the J-Link server should look like this.
 111
 112 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 12.PNG)
 113
 114 Then finally you can use Eclipse debug features to inspect variables, memory, stacktrace, set breakpoints, step over code, etc.
 115
 116 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/debugging.PNG)
 117
 118 If Eclipse can't find your breakpoints and they are ignored then check your path mappings (if using cygwin) or use the other debugging launcher as follows.  Note the 'Select other...' at the bottom of the configuration window.
 119
 120 ![](https://raw.github.com/wiki/cleanflight/cleanflight/images/eclipse-gdb-debugging/config 8 - If breakpoints do not work.PNG)
 121